Skip to content

Conversation

@szehon-ho
Copy link
Member

The generated field spec_id is added to data_file metadata table in #3015

As per #3015 (comment) , this is a late follow up to mark the field id as reserved.

@szehon-ho
Copy link
Member Author

szehon-ho commented May 11, 2022

@rdblue can you see if this is what you meant in this comment #3015 (comment)? Wasn't entirely sure

1. Single-value serialization for lower and upper bounds is detailed in Appendix D.
2. For `float` and `double`, the value `-0.0` must precede `+0.0`, as in the IEEE 754 `totalOrder` predicate. NaNs are not permitted as lower or upper bounds.
3. If sort order ID is missing or unknown, then the order is assumed to be unsorted. Only data files and equality delete files should be written with a non-null order id. [Position deletes](#position-delete-files) are required to be sorted by file and position, not a table order, and should set sort order id to null. Readers must ignore sort order id for position delete files.
4. The following field ids are reserved on `data_file`: 141.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I see. This is for spec_id that doesn't actually appear in the file. This seems reasonable to me.

@rdblue rdblue merged commit abe6ba4 into apache:master May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants